Skip to main content
Version: 9.2

Deployment Jobs

A deployment job executes the type of deployment specified by one or more deployment definitions against one or more target servers. Deployment jobs consist of blocks of instructions, with each block configuring the deployment of one deployment definition to any number of users on one destination server. This enables you to use one deployment job to deploy multiple applications to as many users as necessary, on multiple environments. Deployment jobs require at least one block.

Before You Begin​

Verify that the desired Deployment Definition has been created.

Tip: If you intend to give access to an application to all users from one organization within the same environment, consider making the application public instead of deploying it to all users. This prevents the application from being replicated as copies of the original.

Create a Deployment Job​

  1. In the Qrvey Admin Center, select the Content Deployment icon in the left navigation panel to display the Deployment Jobs tab.

  2. Select Create Job to open the Deployment Job page.

  3. In the fields provided, enter a name and description to replace the placeholder text.

  4. Deployment jobs are made up of one or more blocks that combine configuration information.

    a. In Block 1, use the dropdown lists to group the following:

    • Deployment Definition - Select an existing deployment definition.

    • Destination Server - Select the target server for the deployment.

    • Users - Select one or more target user accounts for the deployed application.

      The page updates to display additional sections containing details about the deployment definition (Definition Summary and Users sections). To display additional information about the entries in a section, select its Details link.

    b. Edit any parameter tokens or content tokens if needed. These values are resolved in the deployment job.

  5. To add a new block, select Add Block and repeat these steps.

    Tip: To deploy one application to several destination servers, create a block for each server.

Edit a Parameter Token​

To review the token details for a user before deploying, select the Details link from an entry in the Users section.

  1. In the deployment job block, display the Deployment Definition Summary section.
  2. Locate the parameter token to configure and select its Configure link.
  3. Enter a value for each user. To use the same value for multiple users, select those users, then select the Bulk Edit link and enter the common value in the field provided.
  4. Select OK to save your changes.

Content Tokens​

A content token is a system-generated parameter that is automatically created for a value that needs to be resolved for each recipient. Created in the deployment definition, the content token is resolved when the deployment job runs. While it uses a {{token}} syntax like the parameter token, this token is assigned by the system and applies to a database object instead of a field name. For example, it identifies entries as application and connection in place of “application name” and “connection username”.

Content Token Use Case​

If a deployment definition is created to update an application, the system assigns the application the content token, {{ user.application }}. Later, in the deployment job, if multiple users are selected as recipients of the deployed application, the system resolves the content token for each user. This enables the deployment job to update the application for each of the recipient users.

After determining the target application to update for each user, all other objects which depend on the selected target application have to be configured. This includes connections, datasets, and so on.

Edit a Content Token​

To successfully deploy, you need to map a content token to existing shared data on the destination server.

  1. In the deployment job, open the Deployment Definition Summary section.

  2. Locate the content token and select its Configure link.

    • If a Configure link is disabled, one or more of its prerequisite content tokens has not been configured.
    • If a deployment job only deploys new content, there are no content tokens to configure.

  3. Configure the destination content using the options provided.

  4. When finished, select OK. The User Destination Content table refreshes to display the mapping.

Run a Deployment Job​

  1. In the Qrvey Admin Center, select the Content Deployment icon in the left navigation panel to display the Deployment Jobs tab.

  2. From the table, select the corresponding job's options menu, then select Edit.

  3. Edit any content tokens if necessary.

  4. Review the deployment definition by selecting its Details link.

  5. Select Deploy.

  6. Select one of the following options for handling failures:

    • Skip the installation for the user that failed and continue installing the remaining users.
    • Deploy anyway for that user despite the broken or faulty assets.

  7. Select OK to run the deployment.

Note: You cannot modify a deployment job after it runs.

Delete a Deployment Job​

To delete an existing deployment job, select its corresponding options menu from the deployment job list, then select Delete.